Skip to content

ci(release): the release commit no longer counts as a feature, so the next merge does not cut a version of its own - #244

Merged
Xyzcancer merged 1 commit into
masterfrom
fix/release-commit-not-a-feature
Nov 17, 2026
Merged

Xyzcancer merged 1 commit into
masterfrom
fix/release-commit-not-a-feature

Conversation

@Xyzcancer

Copy link
Copy Markdown
Contributor

The merged release PR leaves a feat(release): version commit on master, so the next push, even docs or tests only, cut a minor of its own (2.51.0 was such an empty release, and master would now cut 2.53.0).

The commit analyzer now gives that commit no release; every other commit keeps the default rules, and the commit message the release workflows look for stays as it is.

… next merge does not cut a version of its own
@Xyzcancer
Xyzcancer merged commit d1b5abe into master Nov 17, 2026
1 check passed
@Xyzcancer
Xyzcancer deleted the fix/release-commit-not-a-feature branch November 17, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant